Deploying containers on a 5g slice network

ABSTRACT

In an approach to deploying containers on a 5G slice network, responsive to receiving a request to obtain and host a container within a 5G network, a slice network is created within the 5G network for hosting of the container, where the slice network is created by a carrier for the 5G network. The container is deployed to one or more worker nodes using the slice network within the 5G network.

BACKGROUND

The present invention relates generally to the field of network-basedapplications, and more particularly to deploying containers on a 5Gslice network.

A container is a standard unit of software that packages up code and allits dependencies, so the application runs quickly and reliably from onecomputing environment to another. A container image is a lightweight,standalone, executable package of software that includes everythingneeded to run an application: code, runtime, system tools, systemlibraries and settings. A container consists of an entire runtimeenvironment: an application, plus all of its dependencies, libraries,and other binaries, and configuration files it needs to run, bundledinto one package. By containerizing the application platform and itsdependencies, differences in operating system distributions andunderlying infrastructure are abstracted away.

In telecommunications, 5G is the fifth-generation technology standardfor broadband cellular networks, which carriers began deployingworldwide in 2019, and is the planned successor to the 4G networks whichprovide connectivity to most current cellphones. 5G enables a new kindof network that is designed to connect virtually everyone and everythingtogether including machines, objects, and devices. 5G wirelesstechnology is meant to deliver higher multi-Gbps peak data speeds,ultra-low latency, more reliability, massive network capacity, increasedavailability, and a more uniform user experience to more users. Higherperformance and improved efficiency empower new user experiences andconnects new industries. 5G is much more than the next generation ofwireless networks. 5G is the connectivity fabric that will weaveeverything and everyone together.

SUMMARY

Embodiments of the present invention disclose a method, a computerprogram product, and a system for deploying containers on a 5G slicenetwork. In one embodiment, responsive to receiving a request to obtainand host a container within a 5G network, a slice network is createdwithin the 5G network for hosting of the container, where the slicenetwork is created by a carrier for the 5G network. The container isdeployed to one or more worker nodes using the slice network within the5G network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment, in accordance with an embodiment of the presentinvention.

FIG. 2a depicts a block diagram for an embodiment of the 5G containerdistribution program that uses the pull method to deliver a container,in accordance with an embodiment of the present invention.

FIG. 2b depicts a sequence diagram for an embodiment of 5G containerdistribution program 112 that uses the pull method to deliver acontainer, using the system described in FIG. 2a , in accordance with anembodiment of the present invention.

FIG. 3 is a flowchart depicting operational steps for the procedureperformed by the 5G container distribution program to deploy a containerover a 5G slice network using the pull method, in accordance with anembodiment of the present invention.

FIG. 4a depicts a block diagram for an embodiment of the 5G containerdistribution program that uses the push method to deliver a container,in accordance with an embodiment of the present invention.

FIG. 4b depicts a sequence diagram for an embodiment of 5G containerdistribution program that uses the push method to deliver a container,using the system described in FIG. 4a , in accordance with an embodimentof the present invention.

FIG. 5 is a flowchart depicting operational steps for the procedureperformed by the 5G container distribution program to deploy a containerover a 5G slice network using the push method, in accordance with anembodiment of the present invention.

FIG. 6a depicts a block diagram for an embodiment of the 5G containerdistribution program that uses an alternate push method to deliver acontainer, in accordance with an embodiment of the present invention.

FIG. 6b depicts a sequence diagram for an embodiment of 5G containerdistribution program 112 that uses an alternate push method to deliver acontainer, using the system described in FIG. 4a , in accordance with anembodiment of the present invention.

FIG. 7 is a flowchart depicting operational steps for the procedureperformed by the 5G container distribution program to deploy a containerover a 5G slice network using an alternate push method, in accordancewith an embodiment of the present invention.

FIG. 8 depicts a block diagram of components of the computing devicesexecuting the 5G container distribution program within the distributeddata processing environment of FIG. 1, in accordance with an embodimentof the present invention.

DETAILED DESCRIPTION

The growth of 5G networks and cloud-container computing present anopportunity for better performance and lower bandwidth to serveresources to customers. It is common for a container to performdedicated actions for a user in a particular part of the world distantfrom the central computing infrastructure. The present invention enablesa container environment to extend closer to the customer for a temporaryexecution of one of more containers and is controlled through thecarrier. This may be done for several reasons such as being closer tothe source data or shortening the latency in interactions between thecontainer code and the end user. The present invention associates withthe telecom carrier 5G network to identify specific requests requiring acontainer function. The present invention is a computer-implementedmethod, computer program product, and system to adapt the containerenvironment to extend itself into the 5G cloud upon request from theNetwork Functions Virtualization (NFV) of the Virtualized InfrastructureManager (VIM) of the carrier.

In an embodiment, an agreement with a telecommunications carriersupporting a 5G network allows the 5G network to request, obtain andhost a container on a worker node. This allows specific container imagesto execute, while configuring a pre-defined slice network forintegration with the application provider's cluster. This may beachieved through one or a combination of a container system routecontroller, service controller or node controller hereinafter referredto as “controller.” 5G network slicing is a network architecture thatenables the multiplexing of virtualized and independent logical networkson the same physical network infrastructure. Each network slice is anisolated end-to-end network tailored to fulfil diverse requirementsrequested by a particular application. In an embodiment, the VIM of the5G carrier will inform the master node, which has a function known ascloud controller-manager, of the application provider's cluster that anew container is required for a requested function and the VIM wishes tocoordinate the network connection for the container. In response, themaster node will create or cause to be available an appropriate networkresource in the cluster.

In an embodiment, one or more container images are provided to thecarrier for hosting via an interface with the carrier in support of thespecific user request. A one-time request for information resources forthe container image or images is provided in response.

The embodiments described below in FIGS. 2a, 2b , 3, 4 a, 4 b, 5, 6 a, 6b, and 7 allow a third part to be the owner of an application andrelated updates on a subscription basis. The carrier can rely on thethird party to deploy current code and features. The ContinuousIntegration and Continuous Delivery (CICD) pipeline of the softwaresupplier serves one or more carrier VIMs as software service consumers.

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment, generally designated 100, suitable for operationof 5G container distribution program 112 in accordance with at least oneembodiment of the present invention. The term “distributed” as usedherein describes a computer system that includes multiple, physicallydistinct devices that operate together as a single computer system. FIG.3 provides only an illustration of one implementation and does not implyany limitations with regard to the environments in which differentembodiments may be implemented. Many modifications to the depictedenvironment may be made by those skilled in the art without departingfrom the scope of the invention as recited by the claims.

Distributed data processing environment 100 includes computing device110 and container repository 140, both connected to network 120 and 5Gnetwork 130. Network 120 can be, for example, a telecommunicationsnetwork, a local area network (LAN), a wide area network (WAN), such asthe Internet, or a combination of the three, and can include wired,wireless, or fiber optic connections. Network 120 can include one ormore wired and/or wireless networks that are capable of receiving andtransmitting data, voice, and/or video signals, including multimediasignals that include voice, data, and video information. In general,network 120 can be any combination of connections and protocols thatwill support communications between computing device 110 and othercomputing devices (not shown) within distributed data processingenvironment 100. 5G network 130 is a network using 5G technology thatallows deployment of containers to worker nodes.

Computing device 110 can be a standalone computing device, a managementserver, a web server, a mobile computing device, or any other electronicdevice or computing system capable of receiving, sending, and processingdata. In an embodiment, computing device 110 can be a laptop computer, atablet computer, a netbook computer, a personal computer (PC), a desktopcomputer, a personal digital assistant (PDA), a smart phone, or anyprogrammable electronic device capable of communicating with othercomputing devices (not shown) within distributed data processingenvironment 100 via network 120. In another embodiment, computing device110 can represent a server computing system utilizing multiple computersas a server system, such as in a cloud computing environment. In yetanother embodiment, computing device 110 represents a computing systemutilizing clustered computers and components (e.g., database servercomputers, application server computers, etc.) that act as a single poolof seamless resources when accessed within distributed data processingenvironment 100.

In an embodiment, computing device 110 includes 5G containerdistribution program 112. In an embodiment, 5G container distributionprogram 112 is a program, application, or subprogram of a larger programfor deploying containers on a 5G slice network. In an alternativeembodiment, 5G container distribution program 112 may be located on anyother device accessible by computing device 110 via network 120.

In an embodiment, computing device 110 includes information repository114. In an embodiment, information repository 114 may be managed by 5Gcontainer distribution program 112. In an alternate embodiment,information repository 114 may be managed by the operating system of thedevice, alone, or together with, 5G container distribution program 112.Information repository 114 is a data repository that can store, gather,compare, and/or combine information. In some embodiments, informationrepository 114 is located externally to computing device 110 andaccessed through a communication network, such as network 120. In someembodiments, information repository 114 is stored on computing device110. In some embodiments, information repository 114 may reside onanother computing device (not shown), provided that informationrepository 114 is accessible by computing device 110. Informationrepository 114 includes, but is not limited to, VIM configuration data,container configuration data, 5G network configuration data, slicenetwork data, software data, container network security configurationdata, user data, system configuration data, and other data that isreceived by 5G container distribution program 112 from one or moresources, and data that is created by 5G container distribution program112.

Information repository 114 may be implemented using any volatile ornon-volatile storage media for storing information, as known in the art.For example, information repository 114 may be implemented with a tapelibrary, optical library, one or more independent hard disk drives,multiple hard disk drives in a redundant array of independent disks(RAID), solid-state drives (SSD), or random-access memory (RAM).Similarly, information repository 114 may be implemented with anysuitable storage architecture known in the art, such as a relationaldatabase, an object-oriented database, or one or more tables.

Container repository 140 is a data storage that stores all containersthat can be distributed by the 5G container distribution program. Insome embodiments, container repository 140 is owned by the supplier ofcontainers (the seller) who independently enforces container usagecontracts with the consumer (the carrier or the customer of thecarrier). Container repository 140 can accept, reject, log and monitorconsumption of containers (perhaps within the bounds of any contractualarrangement with the carrier). In an embodiment, this information couldfurther be used for billing in another system.

FIG. 2a depicts a block diagram for an embodiment of the 5G containerdistribution program that uses the pull method to deliver a container,generally designated 200 a, in accordance with an embodiment of thepresent invention. In this embodiment, the carrier VIM will inform thecontainer request engine through a message that one or more containersare required to use within the 5G network.

This system includes Carrier VIM 210 a. Carrier VIM 210 a is responsiblefor controlling and managing the compute, storage, and network resourcesof the NFV, usually within infrastructure domain of a carrier oroperator. Carrier VIM 210 a connects to Repository 230 a via Network 220a. Network 220 a is a network, e.g., network 120 from FIG. 1, that isused for out-of-band communications between carrier VIM 210 a andrepository 230 a.

Repository 230 a is a data storage that stores all containers that canbe distributed by the 5G container distribution program. In someembodiments, repository 230 a is owned by the supplier of containers(the seller) who independently enforces container usage contracts withthe consumer (the carrier). Repository 230 a can accept, reject, log andmonitor consumption of containers (perhaps within the bounds of anycontractual arrangement with the carrier). In an embodiment, thisinformation could further be used for billing in another system. MasterNode 240 a is the node which controls and manages a set of worker nodesin a container environment.

Carrier VIM 210 a also connects to 5G Network 250 a. 5G Network 250 a isa 5G network that allows the carrier to request, obtain and host acontainer on a worker node for specific container images to executewhile configuring a pre-defined slice network for integration with theapplication provider's cluster. 5G Network 250 a contains 5G Slice 255a, which is a virtual network on 5G network 250 a created by carrier VIM210 a between master node 240 a and worker node 260 a. 5G slice 255 aconnects master node 240 a to Worker Node 260 a. Worker node 260 a is aninstance of the application environment that executes containers. Workernode 260 a may be a virtual or physical machine, depending on thecluster configuration. Each worker node is managed by master node 240 a.

FIG. 2b depicts a sequence diagram for an embodiment of 5G containerdistribution program 112 that uses the pull method, generally designated200 b, to deliver a container using the system described in FIG. 2a , inaccordance with an embodiment of the present invention. Pull method 200b includes Carrier VIM 210 b, which is carrier VIM 210 a from FIG. 2a ;Repository 230 b, which is repository 230 a from FIG. 2a ; Master Node240 b, which is master node 240 a from FIG. 2 a; 5G Network 250 b, whichis 5G network 250 a from FIG. 2 a; 5G Slice 255 b, which is 5G slice 255a from FIG. 2a ; and Worker Node 260 b, which is worker node 260 a fromFIG. 2 a.

In steps 271 and 272, 5G network slice 255 b is created on 5G network250 b by carrier VIM 210 b. In step 273, carrier VIM 210 b sends the newcluster information, i.e., for network slice 255 b, to master node 240b. In step 274, carrier VIM 210 b sends a request for a container torepository 230 b. Upon confirming acceptance from the VIM of thecontainer pull, a container image is created or made available from arepository 230 b. In this case, the VIM acts as a proxy or arbitrator ofthe container to the container environment.

In step 275, the carrier (possibly via carrier VIM 210 a) then obtains areference or cached copy of the container from an authorized repository,i.e., repository 230 b in this embodiment, and begins deploymentaccording to provided configuration parameters. If required, carrier VIM210 a will establish a slice network for communication between therepository and the application environment which may include the masternode and multiple worker nodes. In step 276, carrier VIM 210 b sends thecontainer image to master node 240 b. In steps 277 and 278, master node240 b sends the container image to worker node 260 b via 5G networkslice 255 b, and the deployment of the container is complete.

In another embodiment of FIG. 2b (not shown), carrier VIM 210 a createsa separate 5G slice (still referred to as 255 b) for the master node 240a to pull the container image from repository 230 a and deploys thecontainer image to worker 260 a over the separate 5g slice 255 b.

FIG. 3 is a flowchart depicting operational steps for the procedureperformed by 5G container distribution program 112 to deploy a containerover a 5G slice network using the pull method, in accordance with atleast one embodiment of the present invention. In an alternativeembodiment, the steps of workflow 300 may be performed by any otherprogram while working with 5G container distribution program 112.

In an embodiment, 5G container distribution program 112 creates a slicenetwork on the 5G network, e.g., 5G network 250 a from FIG. 2a . In anembodiment, 5G container distribution program 112 sends the new clusterinformation for the new slice network to the master node, e.g., masternode 240 a from FIG. 2a . In an embodiment, 5G container distributionprogram 112 requests the desired container from the repository, e.g.,repository 230 a from FIG. 2a . In an embodiment, this request is sentout of band via the out-of-band network, e.g., network 220 a from FIG.2a . In an embodiment, 5G container distribution program 112 receives areference or cached copy of the container image from the repository,e.g., repository 230 a from FIG. 2a . In an embodiment, 5G containerdistribution program 112 deploys the container image to the workernode(s), e.g., worker node 260 a from FIG. 2a , using the master nodecontaining a cloud controller manager and the 5G slice network createdin step 302. 5G container distribution program 112 then ends for thiscycle.

It should be appreciated that embodiments of the present inventionprovide at least for the procedure performed by 5G containerdistribution program 112 to deploy a container over a 5G slice networkusing the pull method. However, FIG. 3 provides only an illustration ofone implementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made by those skilledin the art without departing from the scope of the invention as recitedby the claims.

5G container distribution program 112 creates a slice network (step302). In an embodiment, 5G container distribution program 112 creates aslice network on the 5G network, e.g., 5G network 250 a from FIG. 2a .In an embodiment, 5G container distribution program 112 uses the VIM,e.g., carrier VIM 210 a from FIG. 2a , to create the slice network.

5G container distribution program 112 sends the new cluster informationto the master node (step 304). In an embodiment, 5G containerdistribution program 112 sends the new cluster information for the newslice network to the master node, e.g., master node 240 a from FIG. 2 a.

5G container distribution program 112 requests the container image fromthe repository (step 306). In an embodiment, 5G container distributionprogram 112 requests the desired container from the repository, e.g.,repository 230 a from FIG. 2a . In an embodiment, this request is sentout of band via the out-of-band network, e.g., network 220 a from FIG. 2a.

5G container distribution program 112 receives a copy of the containerimage from the repository (step 308). In an embodiment, 5G containerdistribution program 112 receives a container image from the repository,e.g., repository 230 a from FIG. 2 a.

5G container distribution program 112 deploys the copy of the containerimage to the worker node(s) (step 310). In an embodiment, 5G containerdistribution program 112 deploys the container image to the workernode(s), e.g., worker node 260 a from FIG. 2a , using the master nodeand the 5G slice network created in step 302. 5G container distributionprogram 112 then ends for this cycle.

FIG. 4a depicts a block diagram for an embodiment of the 5G containerdistribution program that uses the push method to deliver a container,generally designated 400 a, in accordance with an embodiment of thepresent invention. This system includes Carrier VIM 410 a. Carrier VIM410 a is responsible for controlling and managing the compute, storage,and network resources of the Network Functions Virtualization (NFV),usually within infrastructure domain of a carrier or operator. CarrierVIM 410 a connects to Repository as the Master Node 430 a via Network420 a. Network 420 a is a network, e.g., network 120 from FIG. 1, thatis used for out-of-band communications between carrier VIM 410 a andrepository as the master node 430 a.

Repository as the master node 430 a is a data storage that stores allcontainers that can be distributed by the 5G container distributionprogram. In some embodiments, repository as the master node 430 a isowned by the supplier of containers (the seller) who independentlyenforces container usage contracts with the consumer (the carrier).Repository as the master node 430 a can accept, reject, log and monitorconsumption of containers (perhaps within the bounds of any contractualarrangement with the carrier). In an embodiment, this information couldfurther be used for billing in another system. Repository as the masternode 430 a is the node which controls and manages a set of worker nodesin a container environment. Repository as the master node 430 a providesthe cloud controller manager functions over the 5G slice.

Carrier VIM 410 a also connects to 5G Network 450 a. 5G Network 450 a isa 5G network that allows the carrier to request, obtain and host acontainer on a worker node for specific container images to executewhile configuring a pre-defined slice network for integration with theapplication provider's cluster. 5G Network 450 a contains 5G Slice 455a, which is a virtual network on 5G network 450 a created by carrier VIM410 a between repository as the master node 430 a and worker node 460 a.5G network slicing is a network architecture that enables themultiplexing of virtualized and independent logical networks on the samephysical network infrastructure. Each network slice is an isolatedend-to-end network tailored to fulfil diverse requirements requested bya particular application. In this embodiment, worker node 460 a iscontained within 5G slice 455 a, and the container is deployed directlyto worker node 460 a from repository as the master node 430 a via 5Gslice 455 a. Worker node 460 a is an instance of the applicationenvironment that executes containers. Worker node 460 a may be a virtualor physical machine, depending on the cluster configuration. Each workernode is managed by repository as the master node 430 a.

FIG. 4b depicts a sequence diagram for an embodiment of 5G containerdistribution program 112 that uses the push method, generally designated400 b, to deliver a container using the system described in FIG. 4a , inaccordance with an embodiment of the present invention.

Push method 400 b includes Carrier VIM 410 b, which is carrier VIM 410 afrom FIG. 4a ; Repository as the Master Node 430 b, which is repositoryas the master node 430 a from FIG. 4 a; 5G Network 450 b, which is 5Gnetwork 450 a from FIG. 4 a; 5G Slice 455 b, which is 5G slice 455 afrom FIG. 4a ; and Worker Node 460 b, which is worker node 460 a fromFIG. 4 a.

In steps 471 and 472, 5G network slice 455 b is created on 5G network450 b by carrier VIM 410 b. In step 473, carrier VIM 410 b sends arequest over any out-of-band network for a container to repository asthe master node 430 b. In this embodiment, the request includes thelocation (address) of the target for the container since repository asthe master node 430 b will push the container directly to worker node460 b via 5G slice 455 b. In steps 474 and 475, repository as the masternode 430 b sends the container image to worker node 460 b via 5G slice455 b. In step 476, repository as the master node 430 b sends anout-of-band message via network 420 b (not shown) to carrier VIM 410 bto notify the VIM that the container has been deployed directly from therepository to the one or more worker nodes using 5G slice 455 b.

FIG. 5 is a flowchart depicting operational steps for the procedureperformed by the 5G container distribution program to deploy a containerover a 5G slice network using the push method, in accordance with anembodiment of the present invention. In an alternative embodiment, thesteps of workflow 500 may be performed by any other program whileworking with 5G container distribution program 112.

In an embodiment, 5G container distribution program 112 creates a slicenetwork on the 5G network, e.g., 5G network 450 a from FIG. 4a , betweenthe repository (which is acting as a master node), e.g., repository asthe master node 430 a from FIG. 4a , and the worker node, e.g., workernode 460 a from FIG. 4a . In an embodiment, 5G container distributionprogram 112 requests the container image from the repository and informsthe repository of the location of the worker node. In an embodiment, 5Gcontainer distribution program 112 receives a notification from therepository that the container has been deployed to the worker node. 5Gcontainer distribution program 112 then ends for this cycle.

It should be appreciated that embodiments of the present inventionprovide at least for the procedure performed by 5G containerdistribution program 112 to deploy a container over a 5G slice networkusing the push method. However, FIG. 5 provides only an illustration ofone implementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made by those skilledin the art without departing from the scope of the invention as recitedby the claims.

5G container distribution program 112 creates a slice network betweenthe repository and the worker node (step 502). In an embodiment, 5Gcontainer distribution program 112 creates a slice network on the 5Gnetwork, e.g., 5G network 250 a from FIG. 2a , between the repository(which is acting as a master node), e.g., repository as the master node430 a from FIG. 4a , and the worker node, e.g., worker node 460 a fromFIG. 4 a.

5G container distribution program 112 requests a container image andinforms the repository of the target location (step 504). In anembodiment, 5G container distribution program 112 requests the containerimage from the repository and informs the repository of the location ofthe worker node. In this embodiment, the repository will deploy thecontainer directly to the worker node, so the repository requires thelocation in the request. In an embodiment, the repository deploys therequested container to the worker node via the 5G slice network.

5G container distribution program 112 receives notification of thecontainer deployment (step 506). In an embodiment, 5G containerdistribution program 112 receives a notification from the repositorythat the container has been deployed to the worker node. 5G containerdistribution program 112 may be configured to maintain or optionallyremove the slice network between the repository and the worker nodedepending on operational needs. 5G container distribution program 112then ends for this cycle.

FIG. 6a depicts a block diagram for an embodiment of the 5G containerdistribution program that uses an alternate push method to deliver acontainer, generally designated 600 a, in accordance with an embodimentof the present invention. This system includes Carrier VIM 610 a.Carrier VIM 610 a is responsible for controlling and managing thecompute, storage, and network resources of the Network FunctionsVirtualization (NFV), usually within infrastructure domain of a carrieror operator. Carrier VIM 610 a connects to Repository 630 a via Network620 a. Network 620 a is a network, e.g., network 120 from FIG. 1, thatis used for out-of-band communications between carrier VIM 610 a andrepository 630 a.

Repository 630 a is a data storage that stores all containers that canbe distributed by the 5G container distribution program. In someembodiments, repository 630 a is owned by the supplier of containers(the seller) who independently enforces container usage contracts withthe consumer (the carrier). Repository 630 a can accept, reject, log andmonitor consumption of containers (perhaps within the bounds of anycontractual arrangement with the carrier). In an embodiment, thisinformation could further be used for billing in another system. MasterNode 640 a is the node which controls and manages a set of worker nodesin a container environment. Repository 630 a connects to master node 640a via Container Delivery 5G Slice 656 a, which is a virtual network on5G network 650 a created by carrier VIM 610 a between repository 630 aand master node 640 a. In this embodiment, the container is deployed toworker nodes 661 a-663 a via container delivery 5G slice 656 a.

Carrier VIM 610 a also connects to 5G Network 650 a. 5G Network 650 a isa 5G network that allows the carrier to request, obtain and host acontainer on a worker node for specific container images to executewhile configuring a pre-defined slice network for integration with theapplication provider's cluster. 5G Network 650 a contains 5G Slice 655a, which is a virtual network on 5G network 650 a created by carrier VIM610 a between master node 640 a and Worker Nodes 661 a-663 a. 5G networkslicing is a network architecture that enables the multiplexing ofvirtualized and independent logical networks on the same physicalnetwork infrastructure. Each network slice is an isolated end-to-endnetwork tailored to fulfil diverse requirements requested by aparticular application. Worker nodes 661 a-663 a are an instance of theapplication environment that executes containers. Worker nodes 661 a-663a may be virtual or physical machines, depending on the clusterconfiguration. Each worker node is managed by master node 640 a.

FIG. 6b depicts a sequence diagram for an embodiment of 5G containerdistribution program 112 that uses an alternate push method, generallydesignated 600 b, to deliver a container using the system described inFIG. 6a , in accordance with an embodiment of the present invention.Alternate push method 600 b includes Carrier VIM 610 b, which is carrierVIM 610 a 6 from FIG. 6a ; Repository 630 b, which is repository 630 afrom FIG. 6a ; Master Node 640 b, which is master node 640 a from FIG.6a ; Container Delivery 5G Slice 656 b, which is container delivery 5Gslice 656 a from FIG. 6a ; and Worker Nodes 661 b-663 b, which areworker nodes 661 a-663 a from FIG. 6 a.

In step 671, carrier VIM 610 b sends a request for a container deliveryto repository 630 b which determines if the request in in compliancewith agreed upon parameters. In step 672, carrier VIM 610 b receives anapproval for the container delivery from repository 630 b. In steps 673and 674, master node 640 b receives the container image from repository630 b via container delivery 5G slice 656 b. In some embodiments, thiscontainer image may be cached by the master node for efficiency. In step675-677, master node 640 b deploys the container image to worker nodes661 b-663 b, respectively, and the deployment of the container iscomplete.

FIG. 7 is a flowchart depicting operational steps for the procedureperformed by the 5G container distribution program to deploy a containerover a 5G slice network using an alternate push method, in accordancewith an embodiment of the present invention. In an alternativeembodiment, the steps of workflow 700 may be performed by any otherprogram while working with 5G container distribution program 112.

In an embodiment, 5G container distribution program 112 requestsapproval from the repository, e.g., repository 630 a from FIG. 6a , todeploy a container to worker node(s), e.g., worker nodes 660 a-661 afrom FIG. 6a . In an embodiment, 5G container distribution program 112receives the approval to deploy the container from the repository. In anembodiment, if the desired container is not cached in the master node,then 5G container distribution program 112 receives the desiredcontainer from the repository, into the master node. In an embodiment,5G container distribution program 112 deploys the container using themaster node via the 5G slice to the worker nodes. 5G containerdistribution program 112 then ends for this cycle.

It should be appreciated that embodiments of the present inventionprovide at least for the procedure performed by the 5G containerdistribution program to deploy a container over a 5G slice network usingan alternate push method. However, FIG. 7 provides only an illustrationof one implementation and does not imply any limitations with regard tothe environments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made by those skilledin the art without departing from the scope of the invention as recitedby the claims.

5G container distribution program 112 requests container deliveryapproval from the repository (step 702). In an embodiment, 5G containerdistribution program 112 requests approval from the repository, e.g.,repository 630 a from FIG. 6a , to deploy a container to worker node(s),e.g., worker nodes 660 a-661 a from FIG. 6a . In this embodiment, thecontainer image may be cached by the master node, thereby avoidinghaving to receive the container image from the repository. In thisembodiment, therefore, container distribution program 112 must getapproval from the repository before deploying the container.

In an embodiment, repository 630 a may apply business logic in theapproval process such as determining the permitted number ofdeployments, rate of usage, functionality restrictions associated withthe properties of the container, and usage limitation agreements withthe owner of the requesting party.

5G container distribution program 112 receives container deliveryapproval from the repository (step 704). In an embodiment, 5G containerdistribution program 112 receives the approval to deploy the containerfrom the repository.

5G container distribution program 112 master node receives the containerimage from the repository (step 706). In an embodiment, if the desiredcontainer is not cached in the master node, then 5G containerdistribution program 112 receives the desired container from therepository, into the master node. In an embodiment, if the master nodealready has a cached copy of the desired container, then containerdistribution program 112 may receive approval for additional deploymentfrom the cache using a number of methods, e.g., a simple indicator ofapproval in a record or the return of a cryptographic key allowing themaster node to decrypt and deploy the container from the cache.

5G container distribution program 112 master node deploys the containerimage to the worker node(s) (step 708). In an embodiment, 5G containerdistribution program 112 deploys the container using the master node viathe 5G slice to the worker nodes. 5G container distribution program 112then ends for this cycle.

FIG. 8 is a block diagram depicting components of computing device 110suitable for 5G container distribution program 112, in accordance withat least one embodiment of the invention. FIG. 8 displays computer 800;one or more processor(s) 804 (including one or more computerprocessors); communications fabric 802; memory 806, includingrandom-access memory (RAM) 816 and cache 818; persistent storage 808;communications unit 812; I/O interfaces 814; display 822; and externaldevices 820. It should be appreciated that FIG. 8 provides only anillustration of one embodiment and does not imply any limitations withregard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.

As depicted, computer 800 operates over communications fabric 802, whichprovides communications between computer processor(s) 804, memory 806,persistent storage 808, communications unit 812, and I/O interface(s)814. Communications fabric 802 may be implemented with any architecturesuitable for passing data or control information between processors 804(e.g., microprocessors, communications processors, and networkprocessors), memory 806, external devices 820, and any other hardwarecomponents within a system. For example, communications fabric 802 maybe implemented with one or more buses.

Memory 806 and persistent storage 808 are computer readable storagemedia. In the depicted embodiment, memory 806 comprises RAM 816 andcache 818. In general, memory 806 can include any suitable volatile ornon-volatile computer readable storage media. Cache 818 is a fast memorythat enhances the performance of processor(s) 804 by holding recentlyaccessed data, and near recently accessed data, from RAM 816.

Program instructions for 5G container distribution program 112 may bestored in persistent storage 808, or more generally, any computerreadable storage media, for execution by one or more of the respectivecomputer processors 804 via one or more memories of memory 806.Persistent storage 808 may be a magnetic hard disk drive, a solid-statedisk drive, a semiconductor storage device, read only memory (ROM),electronically erasable programmable read-only memory (EEPROM), flashmemory, or any other computer readable storage media that is capable ofstoring program instruction or digital information.

The media used by persistent storage 808 may also be removable. Forexample, a removable hard drive may be used for persistent storage 808.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage808.

Communications unit 812, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 812 includes one or more network interface cards.Communications unit 812 may provide communications through the use ofeither or both physical and wireless communications links. In thecontext of some embodiments of the present invention, the source of thevarious input data may be physically remote to computer 800 such thatthe input data may be received, and the output similarly transmitted viacommunications unit 812.

I/O interface(s) 814 allows for input and output of data with otherdevices that may be connected to computer 800. For example, I/Ointerface(s) 814 may provide a connection to external device(s) 820 suchas a keyboard, a keypad, a touch screen, a microphone, a digital camera,and/or some other suitable input device. External device(s) 820 can alsoinclude portable computer readable storage media such as, for example,thumb drives, portable optical or magnetic disks, and memory cards.Software and data used to practice embodiments of the present invention,e.g., 5G container distribution program 112, can be stored on suchportable computer readable storage media and can be loaded ontopersistent storage 808 via I/O interface(s) 814. I/O interface(s) 814also connect to display 822.

Display 822 provides a mechanism to display data to a user and may be,for example, a computer monitor. Display 822 can also function as atouchscreen, such as a display of a tablet computer.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be any tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general-purpose computer, a special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, a segment, or aportion of instructions, which comprises one or more executableinstructions for implementing the specified logical function(s). In somealternative implementations, the functions noted in the blocks may occurout of the order noted in the Figures. For example, two blocks shown insuccession may, in fact, be executed substantially concurrently, or theblocks may sometimes be executed in the reverse order, depending uponthe functionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration but are not intended tobe exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A computer-implemented method comprising:responsive to receiving a request to obtain and host a container withina 5G network, creating, by one or more computer processors, a slicenetwork within the 5G network for hosting of the container, wherein theslice network is created by a carrier for the 5G network; and deploying,by the one or more computer processors, the container to one or moreworker nodes using the slice network within the 5G network.
 2. Thecomputer-implemented method of claim 1, wherein deploying the containerto the one or more worker nodes using the slice network within the 5Gnetwork comprises: sending, by the one or more computer processors, anew cluster information to a master node, wherein the new clusterinformation describes the slice network within the 5G network;requesting, by the one or more computer processors, a container image ofthe container from a repository; receiving, by the one or more computerprocessors, a copy of the container image from the repository; anddeploying, by the one or more computer processors, the copy of thecontainer image to the one or more worker nodes using the slice networkwithin the 5G network.
 3. The computer-implemented method of claim 2,wherein the request for the container image uses an out-of-band networkthat is separate from the 5G network.
 4. The computer-implemented methodof claim 1, wherein deploying the container to the one or more workernodes using the slice network within the 5G network comprises:requesting, by the one or more computer processors, a container image ofthe container from a repository, wherein the request includes a locationof the one or more worker nodes; and receiving, by the one or morecomputer processors, a notification that the repository has deployed thecontainer directly to the one or more worker nodes, wherein thecontainer is deployed directly from the repository to the one or moreworker nodes using the slice network within the 5G network.
 5. Thecomputer-implemented method of claim 4, wherein the repository acts as amaster node for deploying the container to the one or more worker nodes.6. The computer-implemented method of claim 1, wherein deploying thecontainer to the one or more worker nodes using the slice network withinthe 5G network comprises: requesting, by the one or more computerprocessors, a delivery approval from a repository for a container imageof the container; responsive to receiving the delivery approval,receiving, by the one or more computer processors, the container imagefrom the repository, wherein the container image is received by a masternode; and deploying, by the one or more computer processors, thecontainer image to the one or more worker nodes, wherein the containerimage is deployed by the master node using the slice network within the5G network.
 7. The computer-implemented method of claim 6, wherein thecontainer image is received from the repository using a containerdelivery 5G slice, and further wherein the container delivery 5G sliceis a different slice than the slice network within the 5G network.
 8. Acomputer program product comprising one or more computer readablestorage media and program instructions stored on the one or morecomputer readable storage media, the program instructions includinginstructions to: responsive to receiving a request to obtain and host acontainer within a 5G network, create a slice network within the 5Gnetwork for hosting of the container, wherein the slice network iscreated by a carrier for the 5G network; and deploy the container to oneor more worker nodes using the slice network within the 5G network. 9.The computer program product of claim 8, wherein deploy the container tothe one or more worker nodes using the slice network within the 5Gnetwork comprises one or more of the following program instructions,stored on the one or more computer readable storage media, to: send anew cluster information to a master node, wherein the new clusterinformation describes the slice network within the 5G network; request acontainer image of the container from a repository; receive a copy ofthe container image from the repository; and deploy the copy of thecontainer image to the one or more worker nodes using the slice networkwithin the 5G network.
 10. The computer program product of claim 9,wherein the request for the container image uses an out-of-band networkthat is separate from the 5G network.
 11. The computer program productof claim 8, wherein deploy the container to the one or more worker nodesusing the slice network within the 5G network comprises one or more ofthe following program instructions, stored on the one or more computerreadable storage media, to: request a container image of the containerfrom a repository, wherein the request includes a location of the one ormore worker nodes; and receive a notification that the repository hasdeployed the container directly to the one or more worker nodes, whereinthe container is deployed directly from the repository to the one ormore worker nodes using the slice network within the 5G network.
 12. Thecomputer program product of claim 11, wherein the repository acts as amaster node for deploying the container to the one or more worker nodes.13. The computer program product of claim 8, wherein deploy thecontainer to the one or more worker nodes using the slice network withinthe 5G network comprises one or more of the following programinstructions, stored on the one or more computer readable storage media,to: request a delivery approval from a repository for a container imageof the container; responsive to receiving the delivery approval, receivethe container image from the repository, wherein the container image isreceived by a master node; and deploy the container image to the one ormore worker nodes, wherein the container image is deployed by the masternode using the slice network within the 5G network.
 14. The computerprogram product of claim 13, wherein the container image is receivedfrom the repository using a container delivery 5G slice, and furtherwherein the container delivery 5G slice is a different slice than theslice network within the 5G network.
 15. A computer system comprising:one or more computer processors; one or more computer readable storagemedia; and program instructions stored on the one or more computerreadable storage media for execution by at least one of the one or morecomputer processors, the stored program instructions includinginstructions to: responsive to receiving a request to obtain and host acontainer within a 5G network, create a slice network within the 5Gnetwork for hosting of the container, wherein the slice network iscreated by a carrier for the 5G network; and deploy the container to oneor more worker nodes using the slice network within the 5G network. 16.The computer system of claim 15, wherein deploy the container to the oneor more worker nodes using the slice network within the 5G networkcomprises one or more of the following program instructions, stored onthe one or more computer readable storage media, to: send a new clusterinformation to a master node, wherein the new cluster informationdescribes the slice network within the 5G network; request a containerimage of the container from a repository; receive a copy of thecontainer image from the repository; and deploy the copy of thecontainer image to the one or more worker nodes using the slice networkwithin the 5G network.
 17. The computer system of claim 16, wherein therequest for the container image uses an out-of-band network that isseparate from the 5G network.
 18. The computer system of claim 15,wherein deploy the container to the one or more worker nodes using theslice network within the 5G network comprises one or more of thefollowing program instructions, stored on the one or more computerreadable storage media, to: request a container image of the containerfrom a repository, wherein the request includes a location of the one ormore worker nodes; and receive a notification that the repository hasdeployed the container directly to the one or more worker nodes, whereinthe container is deployed directly from the repository to the one ormore worker nodes using the slice network within the 5G network.
 19. Thecomputer system of claim 18, wherein the repository acts as a masternode for deploying the container to the one or more worker nodes. 20.The computer system of claim 15, wherein deploy the container to the oneor more worker nodes using the slice network within the 5G networkcomprises one or more of the following program instructions, stored onthe one or more computer readable storage media, to: request a deliveryapproval from a repository for a container image of the container;responsive to receiving the delivery approval, receive the containerimage from the repository, wherein the container image is received by amaster node; and deploy the container image to the one or more workernodes, wherein the container image is deployed by the master node usingthe slice network within the 5G network.